Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @11ty/eleventy-fetch to v5 #652

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@11ty/eleventy-fetch 4.0.1 -> 5.0.2 age adoption passing confidence

Release Notes

11ty/eleventy-fetch (@​11ty/eleventy-fetch)

v5.0.2: Eleventy Fetch v5.0.2

Compare Source

  • Improved advanced API (you might not need this). Existing default export creates an instance and couples data fetching together. This release adds a Fetch named export to create a Fetch instance without fetching data automatically. Works with the concurrency queue. Use the queue() method to fetch data.
import CachedFetch, { Fetch } from "@​11ty/eleventy-fetch";

let data = await CachedFetch(source, options);

// is the same as:
let inst = Fetch(source, options);
let data = await inst.queue();
  • Adds wasLastFetchCacheHit() on Fetch instances, used to solve bug with Eleventy Image disk cache https://github.com/11ty/eleventy-img/issues/146
  • Improved efficiency: Adds top level instance cache and a few internal caches to avoid duplicate fetch or file system read calls.
  • Adds internal directory manager to avoid duplicate fs.mkdir calls
  • Improved debug logs

Full Changelog: 11ty/eleventy-fetch@v5.0.1...v5.0.2

v5.0.1: Eleventy Fetch v5.0.1

Compare Source

Full Changelog: 11ty/eleventy-fetch@v5.0.0...v5.0.1

v5.0.0: Eleventy Fetch v5.0.0

Compare Source

11ty.dev docs for Fetch have been updated for v5.0.0: https://www.11ty.dev/docs/plugins/fetch/

npm install @​11ty/[email protected]

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

netlify bot commented Nov 16, 2024

Deploy Preview for prismlauncher failed.

Name Link
🔨 Latest commit 73d9ab0
🔍 Latest deploy log https://app.netlify.com/sites/prismlauncher/deploys/677e9cb4d0a7570008a4ba09

@renovate renovate bot force-pushed the renovate/11ty-eleventy-fetch-5.x branch from da182d8 to 96dddcf Compare November 16, 2024 21:58
@renovate renovate bot force-pushed the renovate/11ty-eleventy-fetch-5.x branch from 96dddcf to 73d9ab0 Compare January 8, 2025 15:41
Copy link
Contributor Author

renovate bot commented Jan 8, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
[15:41:33.663] INFO (962): Installing npm [email protected]...
[15:41:34.706] WARN (962): Npm error:
npm info using [email protected]
npm info using [email protected]
npm http fetch GET 200 https://registry.npmjs.org/pnpm 249ms (cache miss)
npm http cache pnpm@https://registry.npmjs.org/pnpm/-/pnpm-9.15.3.tgz 1ms (cache hit)
npm warn cleanup Failed to remove some directories [
npm warn cleanup   [
npm warn cleanup     '/opt/containerbase/tools/pnpm/9.15.3/22.13.0/node_modules',
npm warn cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/containerbase/tools/pnpm/9.15.3/22.13.0/node_modules/pnpm/dist/node_modules'] {
npm warn cleanup       errno: -39,
npm warn cleanup       code: 'ENOTEMPTY',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: '/opt/containerbase/tools/pnpm/9.15.3/22.13.0/node_modules/pnpm/dist/node_modules'
npm warn cleanup     }
npm warn cleanup   ]
npm warn cleanup ]
npm error code ECONNRESET
npm error network aborted
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: /tmp/containerbase-npm-fa24cg/_logs/2025-01-08T15_41_33_765Z-debug-0.log
[15:41:34.727] ERROR (962): npm install command failed
[15:41:34.728] FATAL (962): Install tool pnpm failed in 1s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants